Bridge to Polygon.

Polygon runs its own consensus on top of Ethereum, so a Bridge to Polygon deposit is really two systems handing off state to each other. Your asset is locked in a contract on Ethereum, and Polygon's own chain mints the matching balance on your address almost immediately. Going the other direction is slower by design: Bor produces the blocks that record your exit, but that exit only becomes final on Ethereum once Heimdall rolls it into the next checkpoint. That split — fast entry, checkpoint-gated exit — is the defining shape of this bridge.

Heimdall and Bor: Polygon's Two-Layer Design

Bor is the layer that actually produces Polygon's blocks at high speed, giving the network the throughput that makes everyday fees trivial. Heimdall is a separate proof-of-stake layer made of staked validators whose job is to watch Bor, agree on its state, and periodically commit a summary of it to Ethereum. Neither layer alone secures the chain; it's the pairing that lets Polygon move fast without losing a link to Ethereum's security.

Why Checkpoints Anchor Polygon to Ethereum

A checkpoint is a compressed root hash of a batch of Polygon blocks, submitted to a contract on Ethereum by Heimdall validators. Once that root is on Ethereum, everything inside it — including your withdrawal — can be proven and finalized there. This is why a Bridge to Polygon exit cannot be rushed by paying more gas: it is waiting on the next scheduled checkpoint, not on block space.

Nothing you bring across pays for transactions on Polygon itself — that still takes POL, the asset that fully replaced MATIC as the network's native gas and staking token. If you only carry ETH or USDC through a Bridge to Polygon deposit, your first job on arrival is getting a small amount of POL, either by bringing some along or swapping a sliver of what you brought on a Polygon-native exchange. Validators are paid in POL, staking runs on POL, and every contract call you make afterward is priced in it, so treat it as the one asset you never want to run out of. The migration from MATIC was a token swap, not a rebrand of the same contract — older MATIC balances convert to POL at a fixed ratio, and new deposits, new gas payments and new staking positions on Polygon now reference POL directly rather than the legacy ticker.

Polygon isn't served by a single bridge anymore — PoS, zkEVM and liquidity-based routes all reach it, and picking the wrong one for your destination is the most common mistake. Match the route to where you're actually going before you match it to price.

• Use the PoS bridge for ETH, stablecoins and most ERC-20 tokens when the destination is Polygon PoS and you want the canonical, most liquid wrapped asset.
• Use the zkEVM bridge specifically when you're headed to Polygon zkEVM — it is a separate network from Polygon PoS, and assets do not move between the two automatically.
• Route through an AggLayer-connected path when you want a transfer that can settle across several Polygon chains without re-bridging at each hop.
• Pick a third-party liquidity bridge only when a checkpoint-length wait is unacceptable, and only after checking who actually backs that liquidity.
• Confirm POL is available at the far end regardless of route — none of these deliver gas money along with the asset.

Laid side by side, the trade-off between Polygon's routes is mostly a trade between how official the asset arrives and how long you're willing to wait for it.

Route	Exit Time	Best For
PoS bridge	Checkpoint-bound, hours	Canonical assets, larger transfers
zkEVM bridge	Validity-proof dependent	Moving to/from Polygon zkEVM
Third-party liquidity	Minutes, fronted by a market maker	Urgent exits, smaller amounts

Plasma Exits Are Being Phased Out

Polygon's original Plasma bridge, used for a handful of early assets, relied on a challenge-period exit model rather than checkpoints and is being wound down in favor of the PoS bridge. If you're holding an asset that still references Plasma, moving it onto the PoS path is the more future-proof choice.

The gap between initiating a withdrawal and actually holding the asset on Ethereum again is the part of a Bridge to Polygon round trip that catches people off guard, because nothing about it is broken — it's simply waiting on a scheduled event rather than a transaction.

Why the Checkpoint Window Exists

Submitting every Polygon block individually to Ethereum would be slow and expensive, which defeats the point of a sidechain. Batching thousands of blocks into one checkpoint keeps Ethereum-side costs low for everyone, at the price of withdrawals finalizing in batches rather than the instant they're requested.

Fast-Exit Alternatives

When a checkpoint wait doesn't fit your timeline, a liquidity-backed exit lets a market maker pay you on Ethereum immediately and collect the checkpointed funds later themselves. That convenience is priced into the spread they charge, so it's worth comparing against simply waiting out the window.

Once assets land, Polygon's draw is that you can actually use them without rationing gas. QuickSwap handles most swaps natively on the network, Aave's Polygon deployment covers lending and borrowing at the same sub-cent cost as everything else, and the broader ecosystem of games and NFT marketplaces runs on the same low fee floor. A Bridge to Polygon deposit is only the setup step — the high transaction throughput is what makes using those apps repeatedly, rather than once, actually practical. Stablecoins bridged in this way tend to sit in Aave earning yield or in a QuickSwap liquidity pool rather than idle, precisely because the cost of moving them around again is small enough not to erode the return, something that isn't true for the same strategy run directly on Ethereum.

Every step of a Bridge to Polygon transfer — the deposit, the checkpoint wait, the withdrawal — happens through transactions you sign yourself, with the asset sitting in your own address the entire time rather than in a custodian's ledger.

Allowance Hygiene on Polygon

Each contract you approve on Polygon, from the bridge itself to a DEX or lending market, gets permission to move a specific token up to whatever limit you granted. Checking and trimming those allowances periodically keeps old approvals from sitting around as unnecessary exposure long after you stopped using the app.

Recognizing Phishing Aimed at Bridge Users

Fake bridge interfaces and fake support channels tend to target people mid-transfer, right when they're anxious about a checkpoint delay. Genuine Polygon infrastructure never asks for your recovery phrase at any stage, and a slow withdrawal is a reason to check the checkpoint schedule, not a reason to hand your seed to someone offering to 'speed it up.' Bookmarking the official bridge address and typing it from memory rather than following a link in a message or search ad removes most of the opportunity for a lookalike page to intercept a transfer.